-
-
Notifications
You must be signed in to change notification settings - Fork 398
[skip changelog] Remove protobuf workaround on AppVeyor #329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
We can now switch back to a current version of the protocol since the PR protocolbuffers/protobuf#5044 has been merged to master a released.
@rsora the build on AppVeyor looks fine with protobuf v3.9.1 .. what do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's remove the notice and 🚢
@@ -29,7 +29,7 @@ install: | |||
# protobuf tooling needed at test time. We use a very old version of the compiler | |||
# because of this: https://github.com/protocolbuffers/protobuf/issues/3957 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove this notice now that we can get latest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we get the latest also on the Docker image used for the unix builds on drone.io? Now it's using the v3.8.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah let's consolidate versions across different platforms 👍
I've edited PR title to avoid this to end in the changelog (it doesn't affect users) |
Now we can have the same version on both drone.io and AppVeyor, see PR #329 for the details.
Now we can have the same version on both drone.io and AppVeyor, see PR #329 for the details.
We can now switch back to a current version of the protocol since the
PR protocolbuffers/protobuf#5044 has been
merged to master a released.